CVE-2026-24451
Gitea fork synchronization can expose private parent repository data
Description
Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.
INFO
Published Date :
July 3, 2026, 8:19 p.m.
Last Modified :
July 3, 2026, 8:19 p.m.
Remotely Exploit :
No
Source :
Gitea
Affected Products
The following products are affected by CVE-2026-24451
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update Gitea to a version with the fix.
- Review repository privacy settings carefully.
- Ensure fork synchronization logic is secure.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-24451 vulnerability anywhere in the article.